Method and system for indicating frequency for reporting a geran cgi

ABSTRACT

The present disclosure provides for methods and systems for indicating a frequency for reporting a GERAN CGI. These include the relaxation of the single measurement object per frequency principle; an indication of ARFCN for CGI reading; measurement interruption avoidance; implicit indications of ARFCN for CGI reading; the use of a different object than a measurement object to report the cell for which to report the CGI; the use of a measurement configuration report to indicate the CGI cell or the selection of an ARFCN using to find rules at the UE.

FIELD OF THE DISCLOSURE

The present disclosure relates to measurement reporting between a UserEquipment (UE) and a network element and in one embodiment relates tomeasurement reporting between a UE and an Evolved Universal TerrestrialRadio Access Network (E-UTRAN).

BACKGROUND

A UE may be required to report certain information to a network inaccordance with a measurement configuration provided by the network. Forexample, in a Long Term Evolution (LTE) environment, a measurementconfiguration may be provided by the E-UTRAN, and may use dedicatedsignaling such as an RRCConnectionReconfiguration message when the UE isin an RRC CONNECTED state. The measurement information may be providedto facilitate handover when the UE is approaching a cell boundary or maybe used for other functionality including automatic neighbor relationsfunctions.

Using Third Generation Partnership Project (3GPP) E-UTRANspecifications, the measurement information may be provided based onmeasurement objects. Measurement objects are objects on which the UEperforms measurements and, in some embodiments, are restricted such thatonly one measurement object exists for a particular frequency.

For measurement of LTE and Universal Mobile Terrestrial System (UMTS)systems, only one frequency is assigned per measurement object. However,for measurement of the Global System for Mobile communications (GSM)EDGE Radio Access Network (GERAN), a plurality of frequencies may beassigned to a single measurement object. In some embodiments up to 32frequencies may be assigned to a single measurement object for GERANnetworks.

The use of a plurality of frequencies for GERAN may be problematic incases where the network requires specific information for a specificfrequency. For example, if a GERAN network has a measurement objectwhich measures 3 frequencies and finds a new cell, as reported through aPhysical Cell Identity (PCI), the network may require the Cell GlobalIdentity (CGI) for the new cell. However, if the network utilizes themeasurement object, ambiguity may occur since the measurement objectrelates to 3 frequencies in the above example. If the PCI is reusedbetween these various frequencies then the request for a CGI related toa PCI may be ambiguous at the UE.

In order to remove the ambiguity, the measurement object may bereconfigured. However, this causes significant overhead with regard tosignaling, and complexity with regard to both the network and the UE.Further, the reconfiguring of a measurement object may cause thediscarding of certain information required by the UE with regard to themeasurement object, such as a list of cells which have triggered acertain measurement report, which may lead to degraded systemperformance.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be better understood with reference to thedrawings, in which:

FIG. 1 is a block diagram showing signaling between a user equipment andtwo network entities;

FIG. 2 is a signaling diagram showing the configuration of a secondmeasurement object for reporting CGI;

FIG. 3 is a signaling diagram showing the reconfiguration of ameasurement object with a new information element to report CGI;

FIG. 4 is a signaling diagram showing the reconfiguration of ameasurement object in which the ARFCNs are ordered to provide implicitsignaling;

FIG. 5 is a process diagram showing a process at a UE for selecting anARFCN for which to report the CGI;

FIG. 6 is a process diagram showing a process at a UE for avoidingreconfiguration clearing of information;

FIG. 7 is a signaling diagram showing the sending of a frequency on areportConfig message;

FIG. 8 is a signaling diagram showing the sending of a frequency on ameasurement configuration message;

FIG. 9 is a block diagram of a simplified example network element; and

FIG. 10 is a block diagram of an example user equipment capable of beingused with the embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure provides a method at a user equipment comprising:receiving, at the user equipment, a measurement object from a networkelement for modifying an existing measurement object at the userequipment; and maintaining at least one of a measurement reportingentity, associated timers and any associated information if the receivedmeasurement object is only modified to configure cell global identifierreporting.

The present disclosure further provides a user equipment comprising: aprocessor; and a communications subsystem, wherein the user equipment isconfigured to: receive a measurement object from a network element formodifying an existing measurement object at the user equipment; andmaintain at least one of a measurement reporting entity, associatedtimers and any associated information if the received measurement objectis only modified to configure cell global identifier reporting.

The present disclosure further provides a method at a network elementhaving configured a measurement object at a user equipment with aplurality of frequencies, the method comprising: reconfiguring themeasurement object to indicate a cell global identifier is to bereported on a specific frequency.

The present disclosure further provides a network element adapted toconfigure a measurement object at a user equipment with a plurality offrequencies, the network element comprising: a processor; and acommunications subsystem, wherein the network element is configured to:reconfigure the measurement object to indicate a cell global identifieris to be reported on a specific frequency.

The present disclosure further provides a method at a network elementcommunicating with a user equipment comprising: configuring, from thenetwork element, a first measurement object for a first frequency at theuser equipment; and configuring, from the network element, a secondmeasurement object for the first frequency at the user equipment, thesecond measurement object being only for the reporting of a cell globalidentity.

The present disclosure further provides a network element communicatingwith a user equipment, the network element comprising: a processor; anda communications subsystem, wherein the processor and communicationssubsystem cooperate to: configure a first measurement object for a firstfrequency at the user equipment; and configure from the network element,a second measurement object for the first frequency at the userequipment, the second measurement object being only for the reporting ofa cell global identity.

While the present disclosure is described below with regard to a LongTerm Evolution (LTE) architecture, the methods and systems describedcould be equally applicable to other networks in which measurementobjects are restricted such that only one frequency may be associatedwith a single measurement object. The present disclosure is thereforenot limited to LTE networks.

An E-UTRAN network provides a model for reporting measurementinformation from a UE in accordance with a measurement configurationprovided by the E-UTRAN. A measurement configuration may include variousparameters. Five such parameters are measurement objects; reportingconfigurations; measurement identities; quantity configurations; andmeasurement gaps.

The UE maintains a single measurement object list, a single reportingconfiguration list, and a single measurement identities list. Anymeasurement object can be linked to any reporting configuration of thesame Radio Access Technology (RAT) type through a measurement identity.

With regard to measurement objects, these are the objects on which theUE performs measurements. For intra-frequency and an inter-frequencymeasurement, a measurement object is a single E-UTRA carrier frequency.Associated with this carrier frequency, the E-UTRAN can configure a listof cell or frequency specific offsets and a list of ‘blacklisted’ cells.Blacklisted cells are not considered in event evaluation or measurementreporting.

For inter-RAT UTRA measurements a measurement object is a single UTRAcarrier frequency. Associated with this carrier frequency, the E-UTRANcan configure set of cells

For inter-RAT GERAN measurements a measurement object is a set of GERANcarrier frequencies.

For inter-RAT Code Divisional Multiple Access 2000 (CDMA2000)measurements, a measurement object is a set of cells on a single carrierfrequency.

As seen from above, for LTE, UMTS and CDMA2000, the measurement objectrelates to a single frequency. However, for GERAN, the measurementobject relates to potentially a plurality of carrier frequencies.

A second parameter that may be configured with the measurementconfiguration includes reporting configurations. Reportingconfigurations are provided to a UE in a list, and each has a reportingcriterion in a reporting format. A reporting criterion is a criterionthat triggers the UE to send a measurement report. This can be eitherperiodical or a single event description. The reporting format providesthe quantities that the UE includes in the measurement report andassociated information such as the number of cells to report, forexample.

A third parameter that may be within the measurement configurationincludes measurement identities. Measurement identities are provided ina list and each measurement identity links one measurement object withone reporting configuration. By configuring multiple measurementidentities, it is possible to link more than one measurement object tothe same reporting configuration, as well as to link more than onereporting configuration to the same measurement object. The measurementidentity is used as a reference number in the measurement report. Thus,for example, a measurement identity may link a measurement object with areporting configuration, for example, for Radio Resource Management(RRM) reporting for handover or other purposes and another measurementidentity may link the same measurement object with a second reportingconfiguration that may be provided for automatic neighbor relationfunctions as described below.

A fourth parameter for a measurement configuration may be quantityconfigurations. One quantity configuration is configured per RAT type.The quantity configuration defines the measurement quantities andassociated filtering used for all event evaluation and related reportingof that measurement type. One filter can be configured per measurementquantity.

A fifth parameter for measurement configuration includes a measurementgap. Measurement gaps are the periods that the UE may use to performmeasurements. In other words, the measurement gaps occur when no uplinkor downlink transmissions are scheduled.

Such measurement configurations may be signaled to the UE throughdedicated signaling such as through anRRC_ConnectionReconfigurationMessage and require the UE to report basedon the given configuration.

While the measurement reports might be used for handover purposes, asecond purpose is Automatic Neighbor Relation functions. Historically,Neighbor Relations were provided manually at each cell. However, thiswas burdensome to network carriers and thus an Automatic NeighborRelation (ANR) function was created to relieve the operator from theburden of manually managing these Neighbor Relations. The 3^(rd)Generation Partnership Project, Technical Specification 36.300, “EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN) Overall description Stage 2”,version 11.2.0, Jul. 2, 2012, the contents of which are incorporatedherein by reference, defines a high level overview of the ANRfunctionality. ANR functionality is applicable to intra-frequency,inter-frequency and inter-RAT measurements. Reference is now made toFIG. 1 which explains the inter-frequency or inter-RAT cases.

As seen in FIG. 1, a first cell 110 communicates with a UE 112. When theUE 112 is in a connected mode with cell 110, the eNB of cell 110 caninstruct the UE to perform measurements and detect cells on other RATsor frequencies. The eNB may use different policies for instructing theUE to do the measurement and when to report the measurements to the eNB.To facilitate such reporting, the eNB may need to schedule appropriateidle periods to allow the UE to scan all cells in the target RATs orfrequencies. In the example of FIG. 1, the UE 112 detects a second cell114, including the physical cell identifier (PCI) and the signalstrength of second cell 114.

UE 112 reports the frequency, PCI and signal strength for the detectedcell, as shown by arrow 120 in FIG. 1, to the first cell 110. The PCI isdefined by the carrier frequency and the Primary Scrambling Code (PSC)in the case of a UTRAN Frequency Division Duplex (FDD) cell, by thecarrier frequency in the cell parameter ID in the case of a UTRAN TimeDivision Duplex (TDD) cell, by the band indicator plus the Base StationIdentity Code (BSIC) and the Automatic Radio Frequency Carrier Number(ARFCN) in the case of a GERAN cell and by the Pseudorandom Noise (PN)offset of a CDMA2000 cell.

When the eNB receives the UE report containing PCI(s) of a cell orcells, the eNB may instruct the UE, using the newly discovered PCI as aparameter, to read the CGI and the Routing Area Code (RAC) of thedetected neighbor cell in case of a GERAN detected cell, the CGI,Location Area Code (LAC), RAC and all available Public Land MobileNetwork (PLMN) identities in the case of a UTRAN detected cell, and theCGI in the case of a CDMA2000 detected cell. For an inter-frequencycase, the eNB may instruct the UE, using the newly discovered PCI as aparameter to read the E-UTRAN Cell Global Identifier (ECGI), TrackingArea Code (TAC), and all available PLMN Identifiers of theinter-frequency detected cell. The request is shown in FIG. 1 by arrow122, in which cell 110 requests the CGI for the target physical cellID=5, which matches the cell 114.

Based on the request at arrow 122, UE 112 reads the broadcast controlchannel (BCCH) of cell 114, as shown by arrow 130. The UE may ignoretransmissions from the serving cell while finding the requestedinformation transmitted in the broadcast channel of the detectedinter-system/inter-frequency neighbor cell. In order to do this, the eNBmay need to schedule appropriate idle periods to allow the UE to readthe requested information from the broadcast channel of the detectedinter-RAT/inter-frequency neighbor cell.

After the UE has read the requested information in the new cell, itreports the detected CGI and RAC (in case of GERAN detected cells) orthe CGI, LAC, RAC and PLMN-ID(s) (in the case of UTRAN detected cell) orthe CGI (in the case of a CDMA2000 detected cell) to the serving cellEvolved Node B (eNB). In the inter-frequency case, the UE reports theECGI, the TAC and all PLMN-ID(s) that have been detected. If thedetecting cell is a Closed Subscriber Group (CSG) or hybrid cell, the UEmay also report the CSG ID to the serving cell eNB. The above report isshown in FIG. 1 by arrow 140.

Cell 110 then updates its inter-RAT/inter-frequency Neighbor RelationTable.

The measurement object for a GERAN cell is referred to as aMeasObjectGERAN information element. Reference is now made to Table 1,in which the MeasObjectGERAN information element specifies informationapplicable for inter-RAT GERAN neighboring frequencies.

TABLE 1 MeasObjectGERAN information element -- ASN1START MeasObjectGERAN::= SEQUENCE {  carrierFreqs CarrierFreqsGERAN,  offsetFreqQ-OffsetRangeInterRAT DEFAULT 0,  ncc-Permitted BIT STRING(SIZE (8))DEFAULT ‘11111111’B,  cellForWhichToReportCGI   PhysCellIdGERAN OPTIONAL, -- Need ON  ... } -- ASN1STOP

From Table 1 above, the GERAN measurement object indicates a set offrequencies, CarrierFreqsGERAN in which the UE detects and measures aGERAN cell. A set of GERAN frequencies can be defined in a number ofways. For example, a startingARFCN and followingARFCNs may be providedin an explicit list. Alternatively, equally spaced frequencies or bitmapmay also be provided.

The physical cell identity of the target cell of CGI reportingmeasurement is indicated by the PhysCellIdGERAN. In configuration of ameasurement object, the E-UTRAN only configures a single measurementobject for a given frequency. In other words, it is not possible toconfigure two or more measurement objects for the same frequencies withdifferent associated parameters.

The Information Element CarrierFreqListGERAN defined in 3GPP TS 36.331“Evolved Universal Terrestrial Radio Access (E-UTRA) Radio ResourceControl (RRC)”, v. 11.0.0, Jul. 3, 2012 is used to provide one or moreGERAN ARFCN values, as defined in the 3GPP TS 44.005, “Data Link (DL)Layer, General Aspects”, v. 8.1.0, Mar. 16, 2009, the contents of whichare incorporated herein by reference. The CarrierFreqListGERANrepresents a list of GERAN BCCH carrier frequencies, and are providedbelow with regard to Table 2.

TABLE 2 CarrierFreqsGERAN IE -- ASN1START CarrierFreqsGERAN ::= SEQUENCE{   startingARFCN ARFCN-ValueGERAN,   bandIndicator BandIndicatorGERAN,  followingARFCNs   CHOICE {     explicitListOfARFCNs  ExplicitListOfARFCNs,     equallySpacedARFCNs     SEQUENCE {      arfcn-Spacing     INTEGER (1..8),       numberOfFollowingARFCNs      INTEGER (0..31)     },     variableBitMapOfARFCNs     OCTET STRING(SIZE (1..16))   } } ExplicitListOfARFCNs ::= SEQUENCE (SIZE (0..31)) OFARFCN-ValueGERAN -- ASN1STOP CarrierFreqsGERAN field descriptionsarfcn-Spacing Space, d, between a set of equally spaced ARFCN values.bandIndicator Indicates how to interpret the ARFCN of the BCCH carrier.explicitListOfARFCNs The remaining ARFCN values in the set areexplicitly listed one by one. followingARFCNs Field containing arepresentation of the remaining ARFCN values in the set.numberOfFollowingARFCNs The number, n, of the remaining equally spacedARFCN values in the set. The complete set of (n + 1) ARFCN values isdefined as: {s, ((s + d) mod 1024), ((s + 2 * d) mod 1024) ... ((s + n *d) mod 1024)}. startingARFCN The first ARFCN value, s, in the set.variableBitMapOfARFCNs Bitmap field representing the remaining ARFCNvalues in the set. The leading bit of the first octet in the bitmapcorresponds to the ARFCN = ((s + 1) mod 1024), the next bit to the ARFCN= ((s + 2) mod 1024), and so on. If the bitmap consist of N octets, thetrailing bit of octet N corresponds to ARFCN =((s + 8 * N) mod 1024).The complete set of ARFCN values consists of ARFCN = s and the ARFCNvalues, where the corresponding bit in the bitmap is set to “1”.

As seen in Table 2, the frequencies may be explicit or may be providedby equally spaced frequencies or a variable bit map of frequencies.

From the description above, at least three issues are present. These arethat the setting up of measurement objects specifically for the purposesof CGI reporting may lead to unclear or ambiguous instructions to a UE.Further, in order to overcome the ambiguities, problems may arisethrough the management of measurement objects for reporting of the CGI.Finally, the reconfiguring of a measurement object may lead todisruption of ongoing measurements and the discarding of certaininformation. Each of the above issues is discussed below.

Unclean/Ambiguous GERAN Cells when Reporting CGI

If a GERAN measurement object indicates multiple GSM frequencies and aPCI in the cellForWhichToReportCGI, the network's intentions may beunclear or ambiguous.

The ambiguity may be shown by way of an example. If the GERANmeasurement object includes three frequencies for the UE to scan, namelygf1, gf2 and gf3, the UE may then scan these frequencies for new cells.If the UE detects a new cell on gf2, the UE can provide a measurementresult of a GERAN cell in frequency gf2 using a PCI. The measurementresult contains the PCI, which in the case of a GERAN cell is the BSIC,the ARFCN of gf2, a band indicator and a Received Signal StrengthIndicator (RSSI).

If the network wants to know the CGI of the reported cell, the networkmust currently modify the measurement object to provide the“cellForWhich ToReportCGI” with the PCI for which the network wants theCGI. However, since the measurement object is scanning three frequenciesand since the PCI may be reused between frequencies, if two frequenciescontain the same PCI, it may be unclear which cell the network wants theCGI for.

Utilizing the example above, if both gf1 and gf2 contained a PCI valueof “5”, then the UE would be unsure whether the E-UTRAN wanted the CGIfor the cell on gf1 or the cell on gf2.

The ambiguities are undesirable since they may lead the network to notobtain the desired information.

Further, according to Section 5.5.4.1 of the 3GPP TS 36.331 “EvolvedUniversal Terrestrial Radio Access (E-UTRA) Radio Resource Control(RRC)”, v. 11.0.0, Jul. 3, 2012, the UE needs to consider anyneighboring cell detected on the associated frequency or set offrequencies which has a physical cell identity matching the value of thecellForWhichToReportCGI. Also, it is undesirable to have multiple CGIsreported since this will cause significant processing overhead at theuser equipment. The contents of 3GPP TS 36.331 are incorporated hereinby reference.

Section 5.5.4 of the 3GPP TS 36.331 is reproduced below in Table 3.

TABLE 3 3GPP TS 36.331, Section 5.5.4 Measurement report triggering5.5.4.1 General The UE shall:  1> for each measId included in themeasIdList within VarMeasConfig:    2> if  the  corresponding reportConfig  includes  a  purpose  set  to    reportStrongestCellsForSON:     3> consider any neighbouring celldetected on the associated frequency to be      applicable;    2> elseif the corresponding reportConfig includes a purpose set to reportCGI:    3> consider any neighbouring cell detected on the associatedfrequency/set of      frequencies (GERAN) which has a physical cellidentity matching the value of the      cellForWhichToReportCGI includedin the corresponding measObject within the      VarMeasConfig to beapplicable;

As seen above, ambiguity for a GERAN cell occurs when reporting the CGIif multiple frequencies are utilized.

Managing Measurement Objects

A second issue relates to the management of measurement objects. Inorder to remove the ambiguity discussed above, one option is toreconfigure the measurement object in order to provide for a CGI reportfor a specific frequency. According to the principle that configuringtwo or more measurement objects is not allowed for the same frequencywith different associated parameters, the network needs to configure twoGERAN measurement objects in order to continue on-going measurements andto read the CGI.

For example, utilizing the scenario above, if the three frequencies gf1,gf2 and gf3 are used in a measurement object, and the PCI is found forgf2, the network could modify the existing measurement object to readonly gf1 and gf3 and therefore allow for the on-going measurements ofgf1 and gf3. Further, a new measurement object could be added for theongoing measurement for gf2 and also for reporting the CGI. The newmeasurement object on gf2 would be unambiguous since there is only onefrequency for which the CGI needs to be reported.

Alternatively, the network may remove the existing measurement objectsand add two measurement objects, one for continuing measurements for gf1and gf3 and another for continuing the measurement of gf2 and reportingthe CGI on gf2.

When the reporting of the CGI measurement is completed, the network mayneed to reconfigure the measurement objects to go back to the originalconfiguration that measures all three frequencies.

The separating and integrating measurement objects provided aboveinvolves complicated operations and increases eNB complexity andincreases the size or number of the RRC connection reconfigurationmessages needed.

Reconfiguration Disruptions

In addition to the above, the reconfiguration, including modifying,deleting or creating of measurement objects for CGI reporting, maydisrupt ongoing measurements (layer 3 filtering) or ongoing measurementreporting operations. In accordance with the 3GPP TS 36.331specification, and in particular section 5.5.2.5, as provided in Table 4below, the measurement reporting entry of the measurement identityassociated with the modified measurement object will be removed, theperiodical reporting timer or timer T321 will be stopped, and associatedinformation for the measurement ID will be reset. As a consequence, thelist of cells which triggered measurement reports or other importantinformation to continue the on-going measurements and measurementreporting may be lost, which disrupts on-going measurements andmeasurement reporting. This problem is applicable not only to GERAN, butalso UTRAN and E-UTRAN.

TABLE 4 3GPP TS 36.331, S. 5.5.2.5 Measurement objectaddition/modification The UE shall:  1> for each measObjectId includedin the received measObjectToAddModList:    2> if an entry with thematching measObjectId exists in the measObjectList within the    VarMeasConfig, for this entry:     3> replace the entry with thevalue received for this measObject, except for the      fields cellsToAddModList,  blackCellsToAddModList,  cellsToRemoveList,     blackCellsToRemoveList and measSubframePattemConfig Neigh;    <text omitted>     3> for each measId associated with thismeasObjectId in the measIdList within the      VarMeasConfig, if any:     4> remove the measurement reporting entry for this measId from the       VarMeasReportList, if included;      4> stop the periodicalreporting timer or timer T321, whichever one is running,        andreset the associated information (e.g. timeToTrigger) for this measId;   2> else:     3> add a new entry for the received measObject to themeasObjectList within      VarMeasConfig;

As seen in Table 4, level (4>) paragraphs include the removing of themeasurement reporting entity, the stopping of the periodical reportingtimer or timer T321, and the resetting of associated information.

Based on the UE ambiguities, management of measurement objects, andreconfiguration disruptions, current measurement reporting for GERAN canbe problematic. Reconfiguration disruptions also affect the UTRAN andE-UTRAN.

In order to overcome the above, various embodiments of the presentdisclosure provide for various solutions. These include the relaxationof the measurement object principle; an indication of ARFCN for CGIreading; measurement interruption avoidance; implicit indications ofARFCN for CGI reading; the use of a different object than a measurementobject to report the cell for which to report the CGI; the use of ameasurement configuration report to indicate the CGI cell or theselection of an ARFCN using to find rules at the UE. Each is discussedbelow.

Relaxation of the Measurement Object Principle

In accordance with one embodiment of the present disclosure, anexception to the current principle that the configuring of two or moremeasurement objects is not allowed for the same frequency with differentassociated parameters is provided. In one embodiment, at most twomeasurement objects can have the same frequency when CGI reporting isconfigured. Thus, for example the network is allowed to configure twomeasurement objects for a GERAN frequency.

Such configuration would not be considered an error by the UE and mayhave certain conditions in order to allow the UE to utilize themeasurement objects. Such conditions may include, but are not limitedto:

-   -   a. that exactly one of the measurement objects (referred to as        the CGI measurement object hereafter) is linked via a        measurement identity to a reporting configuration for the        purpose of reporting the CGI;    -   b. that the CGI measurement object is not configured in any        other measurement identity; and/or    -   c. that the CGI measurement object associated with a reporting        configuration having the purpose of reporting the CGI may        contain only 1 frequency and cellForWhichToReportCGI;    -   d. more than one measurement object for a frequency is only        allowed when there are two measurement objects for a frequency        and one measurement object for the frequency has cellForWhich        ToReportCGI and exactly one GERAN frequency, and is not        associated with any reportConfig except optionally one having        reportCGI purpose.

The above conditions may be taken alone or in combination with eachother.

Thus, the network can maintain existing measurement objects withoutchange, and add a new measurement object for CGI reporting only, therebyavoiding possible measurement disruption and also providing for the CGImeasurement in an unambiguous way. The relaxing of the measurementobject principle therefore solves UE ambiguities, and since measurementobject reconfiguration is not needed, there are no issues with managingmeasurement objects or reconfiguration disruptions.

In one embodiment, the second measurement object when configured allowsthe UE to ignore all information elements in the measurement objectother than the carrierFreq(s) and the cellForWhichToReportCGI, as theseare the only information elements needed to report the CGI. Not ignoringother parameters may also lead to ambiguity about which set ofparameters (those from the first measurement object or those from thesecond) apply to the frequency.

Reference is now made to FIG. 2, which shows an example of communicationbetween a network element 210 and a UE 212. In the embodiment of FIG. 2,the network element 210 configures the UE 212 to scan three GERANfrequencies, namely gf1, gf2 and gf3, for RRM reporting in a firstmeasurement object, as seen at arrow 220. In one embodiment, the messageof arrow 220 may be an RRCConnectionReconfiguration message.

As a result of receipt of the first measurement object, UE 212 detectsand reports that it sees a cell on gf2 with a particular PCI. Suchreport is shown by arrow 222 in FIG. 2. In one embodiment, the report ofarrow 222 may be a Measurement Report.

The network element 210 then decides that it wants the CGI for thereported PCI on gf2. In accordance with the present embodiment, networkelement 210 then sends a message, shown by arrow 230, adding a secondmeasurement object in which a single frequency of gf2 is indicated. Thecell for which to report the CGI is set to the PCI reported in themessage at arrow 222. The message of arrow 230 may, in one embodiment bean RRCConnectionReconfiguration message. In addition to adding a secondmeasurement object, the message (e.g. RRCConnectionReconfiguration) addsa new reporting configuration with purpose set to report CGI, and adds anew measurement identity which links the second measurement object withthe new reporting configuration.

As a result of the configuration message at arrow 230, UE 212 then readsthe BCCH of the cell having the PCI on gf2, shown by arrow 232, andsends a report, shown by arrow 240, back to network element 210providing the CGI.

Network element 210 may then delete the second measurement object fromUE 212.

Reference is now made to Tables 5A, 5B and 5C below. Table 5A shows anexample of a modification to the 3GPP TS 36.331 specification, and inparticular to the section 5.5.1 of the specification. The modificationis shown in bold.

TABLE 5A Amendment to 3GPP TS 36.331, section 5.5.1 E-UTRAN onlyconfigures a single measurement object for a given frequency, i.e. it isnot possible to configure two or more measurement objects for the samefrequency with different associated parameters, e.g. different offsetsand/or blacklists. An exception to this rule is that two measurementobjects for a GERAN frequency may be configured provided that exactlyone of them includes a single GERAN frequency andcellForWhichToReportCGI, and the measurement object can be only linkedvia a measurement identity to a reporting configuration with purposereportCGI, and provided that the measurement object is not configured inany other measurement identity. When a second measurement object is soconfigured, all the IEs in that measurement object other thancarrierFreq(s) and cellForWhichToReportCGI shall be ignored. E-UTRAN mayconfigure multiple instances of the same event e.g. by configuring tworeporting configurations with different thresholds.

Alternatively, reference is made to Table 5B, which shows differentphrasing for the specification changes.

TABLE 5B Amendment to 3GPP TS 36.331, section 5.5.1 E-UTRAN onlyconfigures a single measurement object for a given frequency, i.e. it isnot possible to configure two or more measurement objects for the samefrequency with different associated parameters, e.g. different offsetsand/or blacklists. An exception to this rule is that two measurementobjects for a GERAN frequency may be configured. A second measurementobject for a GERAN frequency may be configured for CGI reportingpurpose. This second measurement object shall havecellForWhichToReportCGI and carrierFreqs IEs set with carrierFreqsincluding only one GERAN frequency. All other IEs in the secondmeasurement object shall be ignored. E-UTRAN may configure multipleinstances of the same event e.g. by configuring two reportingconfigurations with different thresholds.

In a further alternative, the above may be simplified in accordance withTable 5C below.

TABLE 5C Amendment to 3GPP TS 36.331, section 5.5.1 E-UTRAN onlyconfigures a single measurement object for a given frequency, i.e. it isnot possible to configure two or more measurement objects for the samefrequency with different associated  parameters,  e.g.  different offsets  and/ or  blacklists,  except cellForWhichToReportCGI. E-UTRANmay configure multiple instances of the same event e.g. by configuringtwo reporting configurations with different thresholds.

As seen in Tables 5A, 5B and 5C, an exception is provided that twomeasurement objects for GERAN frequency may be configured, provided thatexactly one of them includes a single GERAN frequency andcellForWhichToReportCGI and the measurement object is linked through ameasurement identity to a reporting configuration having the purpose ofreportCGI, and provided that the measurement object is not configured inany other measurement identity. In this case, all IEs except for thecarrierFreqs and the cell for which to report CGI are ignored.

In order to signal that a UE is compliant with the above embodiment,various options are possible. In one embodiment, the associated neighborrelation feature has a Feature Group Indicator (FGI) bit. In particular,FGI bit 34 corresponds to GERAN ANR functionality and this bit may betoggled to indicate that the UE supports the multiple measurementobjects for the same frequency. This may be done to prevent the networkfrom requesting a UE that does not support the behavior to report theCGI.

Indication of GERAN ARFCN for CGI Reading

In alternative embodiment, an existing measObjectGERAN may be modifiedby adding a new information element. In particular, the informationelement may add a “carrierFreqForWhichToReportCGI”. This informationelement is, however, merely an example and other information elementsmay be provided.

The addition of the information element which specifies the carrierfrequency for which to report the CGI allows the target cell to beidentified unambiguously. With the information element, the UE canperform ongoing measurements and handle CGI reporting utilizing a singlemeasurement object, thus simplifying protocol operation.

Instead of specifying a frequency, an ARFCN index value may instead bespecified. The index points to the ARFCN for reporting CGI. An exampleof the additional information element definition is provided below withregard to Table 6.

TABLE 6 MeasObjectGERAN information element -- ASN1START MeasObjectGERAN::=   SEQUENCE {   carrierFreqs CarrierFreqsGERAN,   offsetFreqQ-OffsetRangeInterRAT DEFAULT 0,   ncc-Permitted   BIT STRING(SIZE (8))  DEFAULT ‘11111111’B,   cellForWhichToReportCGI   PhysCellIdGERAN  OPTIONAL, -- Need ON   ...,  [[carrierFreqForWhichToreportCGI  ARFCN-ValueGERAN OPTIONAL,  -- Need ON ]] } -- ASN1STOPMeasObjectGERAN field descriptions ncc-Permitted Field encoded as a bitmap, where bit N is set to “0” if a BCCH carrier with NCC = N − 1 is notpermitted for monitoring and set to “1” if a BCCH carrier with NCC = N −1 is permitted for monitoring; N = 1 to 8; bit 1 of the bitmap is theleading bit of the bit string. carrierFreqForWhichToreportCGI Identifiesthe ARFCN for which cellForWhichToReportCGI is reported if more than oneARFCN is configured.

As seen above, the carrierFreqForWhichToreportCGI identifies thefrequency to report if more than one carrier frequency is configured.

Reference is now made to FIG. 3, which shows one example of a networkelement 310 communicating with a UE 312.

As seen at arrow 320, the network element configures a measurementobject for three frequencies, namely gf1, gf2 and gf3.

The UE 312 detects a cell on gf2, and provides a report providing a PCIvalue of the discovered cell, as shown by arrow 322.

After receiving the message at arrow 322, the network element 310decides it would like to receive the CGI value for the new cell, and asa result the network element 310 modifies the measurement object thatwas previously configured at arrow 320 with thecarrierFreqForWhichToreportCGI information element to include the ARFCNassociated with gf2, adds a new reporting configuration in which purposeis set to report CGI, and adds a new measurement identity which linksthe modified measurement object with the new reporting configuration.This is shown by arrow 330 in the example of FIG. 3.

The reconfiguration at arrow 330 may further comprise adding the PCIvalue in the cellForWhichToReportCGI in order to indicate that a CGIreport is required.

Implicit Indication of AFRCN for CGI Reading

In a further embodiment, implicit indication of the frequency for CGIreporting may be performed utilizing current GERAN measurement objects.This may be done, for example, using a startingARFCN andexplicitListOfARFCN. In the present embodiment, the first ARFCN withinthe explicitListOfARFCN may implicitly indicate the frequency for CGIreporting. Alternatively, a different ARFCN in the measurement objectcould be implicitly identified such as the last one, or thestartingARFCN may implicitly indicate the frequency for CGI reporting.Note that when the measurement object contains a single GERAN frequencyand CGI reporting is configured, then the single frequency is used, andthe rule selecting the first frequency in the ExplicitList is not used.

When the network reconfigures the GERAN measurement object for CGIreporting, the network may change the startingARFCN andexplicitListOfARFCN accordingly. While the ARFCN may normally bespecified explicitly, through a bitmap, or using equally spacedfrequencies, the present embodiment limits the specification of theARFCN to an explicit indication.

Reference is now made to Table 7, which shows a carrierFreqsGERANinformation element.

TABLE 7 CarrierFreqsGERAN information element -- ASN1STARTCarrierFreqsGERAN ::= SEQUENCE {   startingARFCN ARFCN-ValueGERAN,  bandIndicator BandIndicatorGERAN,   followingARFCNs   CHOICE {    explicitListOfARFCNs   ExplicitListOfARFCNs,     equallySpacedARFCNsSEQUENCE {       arfcn-Spacing INTEGER (1..8),      numberOfFollowingARFCNs   INTEGER (0..31)     },    variableBitMapOfARFCNs OCTET STRING (SIZE (1..16))   } }ExplicitListOfARFCNs ::=    SEQUENCE (SIZE (0..31)) OF ARFCN-ValueGERAN-- ASN1STOP CarrierFreqsGERAN field descriptions arfcn-Spacing Space, d,between a set of equally spaced ARFCN values. bandIndicator Indicateshow to interpret the ARFCN of the BCCH carrier. explicitListOfARFCNs Theremaining ARFCN values in the set are explicitly listed one by one. IfCGI is to be reported the first ARFCN is the frequency for which CGI isto be reported if multiple frequencies are configured. followingARFCNsField containing a representation of the remaining ARFCN values in theset. numberOfFollowingARFCNs The number, n, of the remaining equallyspaced ARFCN values in the set. The complete set of (n + 1) ARFCN valuesis defined as: {s, ((s + d) mod 1024), ((s + 2 * d) mod 1024) ... ((s +n * d) mod 1024)}. startingARFCN The first ARFCN value, s, in the set.variableBitMapOfARFCNs Bitmap field representing the remaining ARFCNvalues in the set. The leading bit of the first octet in the bitmapcorresponds to the ARFCN = ((s + 1) mod 1024), the next bit to the ARFCN= ((s + 2) mod 1024), and so on. If the bitmap consist of N octets, thetrailing bit of octet N corresponds to ARFCN = ((s + 8 * N) mod 1024).The complete set of ARFCN values consists of ARFCN = s and the ARFCNvalues, where the corresponding bit in the bitmap is set to “1”.

As seen in Table 7 above, the explicitListOfARFCNs is amended toindicate that the first ARFCN is the frequency for which the CGI is tobe reported if multiple frequencies are configured. Modification toexisting specifications are noted in bold.

Reference is now made to FIG. 4, which shows an example ofcommunications between a network element 410 and a UE 412.

The network element 410 sends a configuration message, shown by arrow420, to UE 412, which configures the measurement object. As with theexamples above, in the example of FIG. 4 three frequencies are providedfor the measurement object, namely gf1, gf2 and gf3.

UE 412 subsequently discovers a cell on gf3 and provides a report withthe PCI for the gf3, as shown by arrow 422.

Network element 410 then reconfigures the measurement object, shown byarrow 430. In the reconfiguration, the PCI is added in thecellForWhichToReportCGI, and the ExplicitListOfARFCNs is ordered toreflect the ARFCNs for gf3 and gf2, in that order (in this case, gf1 issent in a startingARFCN). With the reordered ExplicitListOfARFCNs, theUE can then utilize the implicit indication of the first ARFCN toprovide the CGI frequency. The reconfiguration also adds a new reportingconfiguration in which purpose is set to report CGI, and adds a newmeasurement identity which links the modified measurement object withthe new reporting configuration.

The embodiment of FIG. 4 therefore solves the ambiguity issues as wellas the overhead issues required for significant reconfiguration ofmeasurement objects as described above.

Selection of ARFCN by the UE

In a further alternative embodiment, if the GERAN measurement objectcontains two or more ARFCNs, the UE may have a default algorithm withwhich to select the ARFCN for reporting the CGI. For example, in oneembodiment, the UE may select an ARFCN of a cell which has a physicalcell identity equal to the cellForWhichToReportCGI and was most recentlyincluded in a transmitted measurement report of this RRC connection or ameasurement report associated with a GERAN measurement object.

Specifically, the UE may identify ARFCNs of cells which have a physicalcell ID equal to the cell configured in the cellForWhichToReportCGI. Ifonly one such ARFCN is identified, this ARFCN is selected for thefrequency reporting the CGI.

If two or more ARFCNs are identified, the ARFCN may be selected based onthe cell for which the PCI was most recently included in a transmittedmeasurement report of this RRC connection or a measurement reportassociated with a GERAN measurement object. Alternatively, all of theARFCNs for cells that have physical ID equal to thecellForWhichToReportCGI if no such measurement reports have been sentmay be identified.

If two or more ARFCNs still remain after applying the above, then theARFCN of the strongest cell is chosen from those identified above. TheUE can then choose which ARFCN to select among any that are still tieddue to cells with equal strength.

The UE may not need to acquire a CGI if there is no cell with a BSICmatching the cell for which to report CGI.

The above is illustrated with reference to FIG. 5, which shows anexample process at a UE.

The process of FIG. 5 starts at block 510 and proceeds to block 512 inwhich a UE checks whether a cellForWhichToReportCGI contains a PCI andwhether the number of ARFCNs within the monitored frequencies (in themeasurement object) with this PCI is greater than one. If not, theprocess proceeds to block 513 in which a check is made to ensure atleast one ARFCN exists. If not, the process proceeds to block 520 andends. Otherwise, the process proceeds to block 514 in which the CGI ofthe selected ARFCN is read and the process then proceeds to block 516 inwhich the CGI is reported to the network element. From block 516 theprocess proceeds to block 520 and ends.

If, conversely, the check at block 512 determines that there is morethan one ARFCN within the monitored frequencies with a PCI identified inthe cellForWhichToReportCGI, the process proceeds to block 530 in whicha check is made to identify ARFCNs (from those in measurement object) ofcells which have a physical cell ID equal to the cell configured in thecellForWhichToReportCGI that have been most recently reported in thisRRC Connection. If there is more than one such ARFCN then the check atblock 530 is false. From block 530 if there is only one ARFCN, then theprocess proceeds to block 532 in which the most recently reported ARFCNis selected and the process then proceeds to block 514 to detect theCGI.

Conversely, from block 530 if there is more than one such ARFCN then theprocess proceeds to block 540 in which an ARFCN is chosen based on thesignal strength, selecting the strongest ARFCN, i.e. the one with thelargest RSSI measurement.

The process then proceeds to block 542 in which a check is made todetermine whether two or more ARFCNs are still chosen. This could occur,for example, if a plurality of frequencies associated with an ARFCN havethe same signal strength. If yes, the process proceeds from block 542 toblock 544 in which one of the ARFCNs is chosen, e.g. randomly or firstlisted ARFCN, or lowest ARFCN, etc.

From block 544, or from block 542 if the signal strength chooses onlyone ARFCN, the process proceeds to block 514 in which the CGI of theselected ARFCN is detected and the process then proceeds to block 516 inwhich the CGI is reported.

The behavior may be implemented using the measObjectGERAN informationelement, as defined by 3GPP TS 36.331, as shown in Table 8 below.

TABLE 8 MeasObjectGERAN information element -- ASN1START MeasObjectGERAN::= SEQUENCE {     carrierFreqs CarrierFreqsGERAN,     offsetFreq Q-OffsetRangeInterRAT DEFAULT 0,     ncc-Permitted BIT STRING(SIZE (8))    DEFAULT ‘11111111’B,     cellForWhichToReportCGI PhysCellIdGERANOPTIONAL,   -- Need ON     ... } -- ASN1STOP MeasObjectGERAN fielddescriptions ncc-Permitted Field encoded as a bit map, where bit N isset to “0” if a BCCH carrier with NCC = N − 1 is not permitted formonitoring and set to “1” if a BCCH carrier with NCC = N − 1 ispermitted for monitoring; N = 1 to 8; bit 1 of the bitmap is the leadingbit of the bit string. cellForWhichToReportCGI Indicates the physicalcell Identity of the cell whose CGI to be reported. If carrierFreqscontains two or more ARFCNs, the UE selects the ARFCN of a cell whichhas the physical cell identity equal to cellForWhichToReportCGI. Ifthere are two or more such ARFCNs, the UE selects an ARFCN of a cellwhich has the physical cell identity equal to cellForWhichToReportCGIand was most recently included in a transmitted measurement report ofthis RRC connection or a transmitted measurement report associated withthe GERAN measurement object. If there are still two or more such ARFCNsselect an ARFCN of the strongest cell.

The cellForWhichToReportCGI is modified to indicate that the physicalcell identity of the cell for which the CGI is to be reported is chosenbased on the description in Table 8. If there are two or morefrequencies configured in GERAN measurement objects, the following stepsof selection criteria may be performed. 1) identify a ARFCN of a cellwhich has the indicated PCI. If a single ARFCN is identified, select theARFCN. 2) If two or more such ARFCNs are identified, identify an ARFCNof a cell which meets the above condition and which was most recentlyincluded in a transmitted measurement report of this RRC connection orin a transmitted measurement report associated with the GERANmeasurement object. If a single ARFCN is identified, select the ARFCN.3) If two or more such ARFCNs are identified, identify a ARFCN of a cellwhich meets the above two conditions and which is the strongest cell inthe measurement report or is the strongest cell currently. If there aremultiple cells with the same strength, select any of them.

Based on the above, once the network element modifies the measurementobject to indicate a PCI within the cellForWhichToReportCGI, the UE canthus perform its own conflict resolution to determine the appropriatecell. Further, the network may be aware of the contention based rulesand thus may know, without ambiguity, which frequency the UE willreport.

Measurement Interruption Avoidance

In all of the embodiments described above with reference to FIGS. 3, 4and 5, the measurement object is modified. Namely, in the embodimentassociated with FIG. 3, an information element to specify the frequencyis provided. In the embodiment associated with FIG. 4, the explicit listof ARFCNs is sorted to provide an implicit indication of the frequencyfor which to find the CGI. In the embodiment of FIGS. 3, 4 and 5, thePCI value is set in the cellForWhichToReportCGI information element.Thus, based on the modification to the measurement object, the layer 3filtering or measurement reporting may be interrupted based on the 3GPPTS 36.331 specification, and in particular section 5.5.2.5.

In order to avoid this, the embodiments of any of the above may bemodified to add an exception to avoid interruption.

Thus, when requesting CGI reporting, the network may modify an existingmeasurement object. However, on the UE side, when the modification of ameasurement object is set in the cellForWhichToReportCGI, and any of theother modifications with regard to FIG. 3, 4 or 5 are made, the UE maymaintain the measurement reporting entity, continue the periodicalreporting timer or timer T321, if running, and not reset the associatedinformation.

TABLE 9 Section 5.5.2.5 Measurement object addition/modification 5.5.2.5Measurement object addition/modification The UE shall:  1> for eachmeasObjectId included in the received measObjectToAddModList:   2> if anentry with the matching measObjectId exists in the measObjectList withinthe    VarMeasConfig, for this entry:    3> replace the entry with thevalue received for this measObject, except for the     fields cellsToAddModList,  blackCellsToAddModList,  cellsToRemoveList,    blackCellsToRemoveList and measSubframePatternConfigNeigh;    <textomitted>   3> if  this  measObject  is  not  modified  to  only configure    cellForWhichToReportCGI:    4> for each measId associatedwith this measObjectId in the measIdList within    the VarMeasConfig, ifany:     5>   remove the measurement reporting entry for this measIdfrom the      VarMeasReportList, if included;     5>   stop theperiodical reporting timer or timer T321, whichever one is      running,and reset the associated information (e.g. timeToTrigger) for this     measId;   2> else:    3> add a new entry for the receivedmeasObject to the measObjectList within     VarMeasConfig;

As seen in Table 9 above, text may be added to the 3GPP TS 36.331specification, and in particular to section 5.5.2.5, which provides theprecondition that the measurement object is not modified to onlyconfigure the cell for which to report CGI. Thus, based on the amendedtext, as shown in bold, if the modification of the measurement object isonly for the cellForWhichToReportCGI, the UE skips the removal of themeasurement reporting entity and the stopping of the timers. Thisapplies to the solution in FIG. 5. For the solutions of FIGS. 3 and 4,additional modifications to the measurement object may be allowedwithout executing the remove and reset behavior. These additionalmodifications could be to allow an ARFCN to be added to the IEcarrierFreqForWhichToreportCGI or the StartingARFCN and ExplicitList tobe provided to re-order (but not change) the frequencies in themeasurement object.

Reference is now made to FIG. 6, which shows an example process at auser equipment for avoiding reconfiguration issues for CGI reporting.The process of FIG. 6 starts at block 610 and proceeds to block 612 inwhich a check is made to determine whether or not a reconfiguredmeasurement object has been received at the UE. If no, the processproceeds back to block 612 until a reconfigured measurement object isreceived.

Once a reconfigured measurement object is received, the process proceedsto block 614 in which a check is made to determine whether thereconfiguration of the measurement object is only for CGI reporting. Ifno, the process proceeds to block 620 in which the measurement reportingentity for the measurement ID is removed, the periodical reporting timeror timer T321 are stopped and the associated information is reset.

The process then proceeds from block 620 to block 622 and ends.

From block 614, if the reconfigured measurement object is only modifiedfor CGI reporting, the process proceeds directly to block 622 and ends.

The process of FIG. 6 can be applied to the embodiments of any of FIG.3, 4 or 5.

Further, the reporting of the CGI may use a new measurement identity andreporting configuration in some embodiments. Reference is made to Table10 below.

TABLE 10 Section 5.5.2.3 Measurement identity addition/modification5.5.2.3 Measurement identity addition/modification E-UTRAN applies theprocedure as follows:  -  configure a measId only if the correspondingmeasurement object, the corresponding   reporting configuration and thecorresponding quantity configuration, are configured;  -  may add a newmeasId and a new reportConfig for reporting CGI; The UE shall:  1> foreach measId included in the received measIdToAddModList:   2> if anentry with the matching measId exists in the measIdList within the   VarMeasConfig:    3> replace the entry with the value received forthis measId;   2> else:    3> add a new entry for this measId within theVarMeasConfig ;   2> remove the measurement reporting entry for thismeasId from the    VarMeasReportList, if included;   2> stop theperiodical reporting timer or timer T321, whichever one is running, and   reset the associated information (e.g. timeToTrigger) for thismeasId;   2> if the triggerType is set to periodical and the purpose isset to reportCGI in the    reportConfig associated with this measId:   3> if the measObject associated with this measId concerns E-UTRA:     <text omitted>    3> else if the measObject associated with thismeasId concerns UTRA:    <text omitted>    3> else:     4> start timerT321 with the timer value set to 8 seconds for this measId;

As seen from Table 10, the 3GPP TS 36.331 specification, and inparticular section 5.5.2.3 are modified to include a new measurement IDand new reporting configuration for reporting the CGI. The adding of thenew measurement ID and reporting configuration are optional but canprovide a cleaner transaction and avoid unnecessary measurementinterruption by providing a separate reporting configuration andmeasurement ID for the reporting of the CGI. This could again beimplemented with regard to any of the embodiments of FIG. 3, 4 or 5above.

reportConfig Signaling

In a further alternative embodiment, in order to avoid possibledisruption of on-going measurements such as layer 3 filtering inmeasurement reporting upon configuring the reporting of the CGI, thepresent embodiment provides for signaling information elements for thecellForWhichToReportCGI in a “report configuration”, rather than for ameasurement object. In this way, the modification of the existingmeasurement object can be avoided, thereby avoiding the problemsassociated with the resetting or the reconfiguration of the measurementobject.

The E-UTRAN may add a new reportConfig for reporting the CGI to avoidthe possible measurement or measurement reporting disruptions.Alternatively, the E-UTRAN may modify an existing reportingconfiguration which is or is not associated with the measurement objectto be used for reporting the CGI. This may be applicable for all of theGERAN, UTRAN and E-UTRAN.

For example, in E-UTRAN, the physical cell identity may be added to thereportConfig E-UTRA information element. Reference is now made to Table11 below.

TABLE 11 ReportConfigEUTRA information element ReportConfigEUTRAinformation element -- ASN1START ReportConfigEUTRA ::= SEQUENCE {  triggerType CHOICE {     event SEQUENCE {       eventId CHOICE {        eventA1 SEQUENCE {           a1-Threshold ThresholdEUTRA        },         eventA2 SEQUENCE {           a2-ThresholdThresholdEUTRA         },         eventA3 SEQUENCE {           a3-OffsetINTEGER (−30..30),           reportOnLeave BOOLEAN         },        eventA4 SEQUENCE {           a4-Threshold ThresholdEUTRA        },         eventA5 SEQUENCE {           a5-Threshold1ThresholdEUTRA,           a5-Threshold2 ThresholdEUTRA         },        ...,         eventA6-r10 SEQUENCE {           a6-Offset-r10INTEGER (−30..30),           a6-ReportOnLeave-r10 BOOLEAN         }      },       hysteresis Hysteresis,       timeToTrigger TimeToTrigger    },     periodical SEQUENCE {       purpose ENUMERATED {reportStrongestCells, reportCGI}     }   },   triggerQuantity ENUMERATED{rsrp, rsrq},   reportQuantity ENUMERATED {sameAsTriggerQuantity, both},  maxReportCells INTEGER (1..maxCellReport),   reportIntervalReportInterval,   reportAmount ENUMERATED {r1, r2, r4, r8, r16, r32,r64, infinity},   ...,   [[  si-RequestForHO-r9 ENUMERATED {setup}  OPTIONAL, -- Cond reportCGI     ue-RxTxTimeDiffPeriodical-r9ENUMERATED {setup}   OPTIONAL  -- Need OR   ]],   [[ includeLocationInfo-r10 ENUMERATED {true}   OPTIONAL, -- Cond reportMDT    reportAddNeighMeas-r10 ENUMERATED {setup}   OPTIONAL  -- Need OR  ]],   [[  cellForWhichToReportCGI PhysCellId OPTIONAL,-- CondreportCGI   ]] } ReportConfigEUTRA field descriptions <rows omitted>cellForWhichToReportCGI Indicates the physical cell id for which CGI isreported. This information element overrides cellForWhichToReportCGI ifindicated in measObjectEUTRA.

As seen above, for the E-UTRA, the “cellForWhichToReportCGI” is added tothis information element. Further, the information element may overridethe cell for which to report CGI if indicated in the measObjectEUTRA.

Similarly, for UTRAN and GERAN, the physical cell identity and frequencyinformation (band indicator plus ARFCN) may be added to the reportConfiginter-RAT information element. Reference is now made to Table 12.

TABLE 12 ReportConfigInterRAT information element ReportConfigInterRATinformation element -- ASN1START ReportConfigInterRAT ::= SEQUENCE {triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB1 SEQUENCE{ b1-Threshold CHOICE { b1-ThresholdUTRA ThresholdUTRA,b1-ThresholdGERAN ThresholdGERAN, b1-ThresholdCDMA2000 ThresholdCDMA2000} }, eventB2 SEQUENCE { b2-Threshold1 ThresholdEUTRA, b2-Threshold2CHOICE { b2-Threshold2UTRA ThresholdUTRA, b2-Threshold2GERANThresholdGERAN, b2-Threshold2CDMA2000 ThresholdCDMA2000 } }, ... },hysteresis Hysteresis, timeToTrigger TimeToTrigger }, periodicalSEQUENCE { purpose ENUMERATED { reportStrongestCells,reportStrongestCellsForSON, reportCGI} } }, maxReportCells INTEGER(1..maxCellReport), reportInterval ReportInterval, reportAmountENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, ..., [[ si-RequestForHO-r9 ENUMERATED {setup} OPTIONAL  -- Cond reportCGI ]],[[  reportQuantityUTRA-FDD-r10 ENUMERATED {both} OPTIONAL  -- Need OR]], [[  cellForWhichToReportCGIIRAT-r10 CellForWhichToReportCGIIRAT-r10OPTIONAL -- Cond reportCGI  ]] } CellForWhichToReportCGIIRAT::= SEQUENCE{  physCellId-r10  CHOICE {   utra-FDD PhysCellIdUTRA-FDD,    utra-TDDPhysCellIdUTRA-TDD,   geran PhysCellIdGERA  }, carrierFreqForWhichToreportCGI   CarrierFreqGERAN   OPTIONAL,  -- NeedON } ReportConfigIRAT field descriptions <rows omitted>cellForWhichToReportCGIIRAT Indicates the physical cell id for which CGIis reported. This information element overrides cellForWhichToReportCGIif indicated in corresponding measurement object. In case of GERAN, thefrequency carrierFreqForWhichToreportCGI may be indicated.

For Table 12, information regarding the PCI for which to report the CGImay also be added to the information element along with the carrierfrequency for which to report the CGI. The carrier frequency would beadded in the GERAN case only and not in the UTRAN case as in the UTRANcase there is already a unique frequency in the measurement object.

Thus, reference is now made to FIG. 7. In FIG. 7 a network element 710communicates with a UE 712. The network element 710 sends aconfiguration message shown by arrow 720 indicating the configuration ofgf1, gf2 and gf3 as discussed above with reference to FIGS. 2 to 4.

The UE then detects a cell and reports the frequency and the PCI, asshown by arrow 722.

Unlike the solutions above, the network element does not modify themeasurement object but instead sends a message containing a reportConfigin which the cellForWhichToReportCGI is provided and adds a newmeasurement identity, which is sent to link the reportConfig with themeasurement object, shown by arrow 730 in FIG. 7.

measConfig for Reporting the CGI

Alternatively, instead of using the reportConfig as identified withregard to the embodiment of FIG. 7 above, the cell for which to reportthe CGI can be reported in the measurement configuration. In accordancewith section 5.2.2 of the 3GPP TS 36.331 specification, the E-UTRANguarantees that anytime a UE is acquiring CGI information, it is doingso for only one cell. However, the current specification unnecessarilyallows multiple measurement objects to have the cellForWhichToReportCGIconfigured. Thus, multiple reporting configurations may have a purposeset to reportCGI.

Instead, by signaling the cellForWhichToReportCGI in the measurementconfiguration, the rule for reporting only one CGI at a time can beenforced by the protocol itself.

Further, by using the measurement configuration instead of a measurementobject, the modification of measurement objects is avoided, thusavoiding the issues identified above.

Reference is now made to Table 13, which shows the additionalinformation added to a 3GPP TS 36.311 measConfig information element.

TABLE 13 MeasConfig information element -- ASN1START MeasConfig ::=SEQUENCE { -- Measurement objects measObjectToRemoveListMeasObjectToRemoveList OPTIONAL, -- Need ON measObjectToAddModListMeasObjectToAddModList OPTIONAL, -- Need ON -- Reporting configurationsreportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need ONreportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need ON-- Measurement identities measIdToRemoveList MeasIdToRemoveListOPTIONAL, -- Need ON measIdToAddModList MeasIdToAddModList OPTIONAL, --Need ON -- Other parameters quantityConfig QuantityConfig OPTIONAL, --Need ON measGapConfig MeasGapConfig OPTIONAL, -- Need ON s-MeasureRSRP-Range OPTIONAL, -- Need ON preRegistrationInfoHRPDPreRegistrationInfoHRPD OPTIONAL, -- Need OP speedStatePars CHOICE {release NULL, setup SEQUENCE { mobilityStateParametersMobilityStateParameters, timeToTrigger-SF SpeedStateScaleFactors } }OPTIONAL,  -- Need ON ..., [[ cellForWhichToReportCGIIRATCellForWhichToReportCGIIRAT OPTIONAL -- Cond reportCGI  ]] }CellForWhichToReportCGIIRAT::= SEQUENCE {  physCellId CHOICE {   eutra PhysCellId,   utra-FDD PhysCellIdUTRA-FDD,   utra-TDDPhysCellIdUTRA-TDD,   gera  PhysCellIdGERA  }, carrierFreqForWhichToreportCGI   CarrierFreqGERAN   OPTIONAL, -- NeedON}

As seen in the table above, when requesting the UE to report the CGI,the E-UTRAN may add an instance of a reporting configuration with apurpose set to reportCGI and set the additional information in themeasurement configuration to specify the target cell. Alternatively, thenetwork may modify existing instances of reporting configurations whichare not associated with the measurement object to be used for reportingthe CGI.

In yet another embodiment, the network may set theCellForWhichToReportCGIIRAT in measurement configuration with a reservedmeasurement identity for CGI reporting. The reserved measurementidentity is not linked to a measurement object or a reportingconfiguration.

Reference is now made to FIG. 8 which shows example signaling between anetwork element 810 and a user equipment 812. The network element 810configures a measurement object and in the example of FIG. 8 configuresthree GERAN frequencies, namely gf1, gf2 and gf3, as shown in arrow 820.

UE 812 detects a cell on gf2 and reports the PCI of the cell, as shownby arrow 822.

Instead of reconfiguring the measurement object, if the network elementwants the CGI associated with the PCI received at arrow 822, the networkelement may send a measurement configuration in which the frequency maybe provided for reporting the CGI. For example, the ARFCN associatedwith gf2 may be provided as part of the measurement configuration. Thisis shown by arrow 830 in FIG. 8.

With any of the above, the FGI bit, for example FGI bit 34, may betoggled to indicate whether or not the UE has adopted the embodimentsdescribed herein. Thus if the bit is toggled, the UE may accept themodified measurement object, reportConfig, or measurement configmessages. Conversely, if the bit is not toggled, this may signal to thenetwork that the UE uses an older version of the LTE specification andthus not to utilize the embodiments described above. More generally someother method could be used to allow the E-UTRAN to know whether UE hasimplemented one of the above methods, e.g. a capability indication or arelease indicator.

The above may be implemented by any network element. A simplifiednetwork element is shown with regard to FIG. 9. The network element ofFIG. 9 may be an eNB or other network element, including networkelements 210, 310, 410, 710 or 810, among others.

In FIG. 9, network element 910 includes a processor 920 and acommunications subsystem 930, where the processor 920 and communicationssubsystem 930 cooperate to perform the methods described above.

Further, the above may be implemented by any UE. One exemplary device isdescribed below with regard to FIG. 10.

UE 1000 is typically a two-way wireless communication device havingvoice and data communication capabilities. UE 1000 generally has thecapability to communicate with other computer systems on the Internet.Depending on the exact functionality provided, the UE may be referred toas a data messaging device, a two-way pager, a wireless e-mail device, acellular telephone with data messaging capabilities, a wireless Internetappliance, a wireless device, a mobile device, or a data communicationdevice, as examples.

Where UE 1000 is enabled for two-way communication, it may incorporate acommunication subsystem 1011, including both a receiver 1012 and atransmitter 1014, as well as associated components such as one or moreantenna elements 1016 and 1018, local oscillators (LOs) 1013, and aprocessing module such as a digital signal processor (DSP) 1020. As willbe apparent to those skilled in the field of communications, theparticular design of the communication subsystem 1011 will be dependentupon the communication network in which the device is intended tooperate. The radio frequency front end of communication subsystem 1011can be any of the embodiments described above.

Network access requirements will also vary depending upon the type ofnetwork 1019. In some networks network access is associated with asubscriber or user of UE 1000. A UE may require a removable useridentity module (RUIM) or a subscriber identity module (SIM) card. TheSIM/RUIM interface 1044 is normally similar to a card-slot into which aSIM/RUIM card can be inserted and ejected. The SIM/RUIM card can havememory and hold many key configurations 1051, and other information 1053such as identification, and subscriber related information.

When required network registration or activation procedures have beencompleted, UE 1000 may send and receive communication signals over thenetwork 1019. As illustrated in FIG. 10, network 1019 can consist ofmultiple base stations communicating with the UE.

Signals received by antenna 1016 through communication network 1019 areinput to receiver 1012, which may perform such common receiver functionsas signal amplification, frequency down conversion, filtering, channelselection and the like. A/D conversion of a received signal allows morecomplex communication functions such as demodulation and decoding to beperformed in the DSP 1020. In a similar manner, signals to betransmitted are processed, including modulation and encoding forexample, by DSP 1020 and input to transmitter 1014 for digital to analogconversion, frequency up conversion, filtering, amplification andtransmission over the communication network 1019 via antenna 1018. DSP1020 not only processes communication signals, but also provides forreceiver and transmitter control. For example, the gains applied tocommunication signals in receiver 1012 and transmitter 1014 may beadaptively controlled through automatic gain control algorithmsimplemented in DSP 1020.

UE 1000 generally includes a processor 1038 which controls the overalloperation of the device. Communication functions, including data andvoice communications, are performed through communication subsystem1011. Processor 1038 also interacts with further device subsystems suchas the display 1022, flash memory 1024, random access memory (RAM) 1026,auxiliary input/output (I/O) subsystems 1028, serial port 1030, one ormore keyboards or keypads 1032, speaker 1034, microphone 1036, othercommunication subsystem 1040 such as a short-range communicationssubsystem and any other device subsystems generally designated as 1042.Serial port 1030 could include a USB port or other port known to thosein the art.

Some of the subsystems shown in FIG. 10 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 1032 and display1022, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the processor 1038 may be stored in apersistent store such as flash memory 1024, which may instead be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that the operating system, specificdevice applications, or parts thereof, may be temporarily loaded into avolatile memory such as RAM 1026. Received communication signals mayalso be stored in RAM 1026.

As shown, flash memory 1024 can be segregated into different areas forboth computer programs 1058 and program data storage 1050, 1052, 1054and 1056. These different storage types indicate that each program canallocate a portion of flash memory 1024 for their own data storagerequirements. Processor 1038, in addition to its operating systemfunctions, may enable execution of software applications on the UE. Apredetermined set of applications that control basic operations,including at least data and voice communication applications forexample, will normally be installed on UE 1000 during manufacturing.Other applications could be installed subsequently or dynamically.

Applications and software may be stored on any computer readable storagemedium. The computer readable storage medium may be a tangible or intransitory/non-transitory medium such as optical (e.g., CD, DVD, etc.),magnetic (e.g., tape) or other memory known in the art.

One software application may be a personal information manager (PIM)application having the ability to organize and manage data itemsrelating to the user of the UE such as, but not limited to, e-mail,calendar events, voice mails, appointments, and task items. Naturally,one or more memory stores would be available on the UE to facilitatestorage of PIM data items. Such PIM application may have the ability tosend and receive data items, via the wireless network 1019. Furtherapplications may also be loaded onto the UE 1000 through the network1019, an auxiliary I/O subsystem 1028, serial port 1030, short-rangecommunications subsystem 1040 or any other suitable subsystem 1042, andinstalled by a user in the RAM 1026 or a non-volatile store (not shown)for execution by the processor 1038. Such flexibility in applicationinstallation increases the functionality of the device and may provideenhanced on-device functions, communication-related functions, or both.For example, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing the UE 1000.

In a data communication mode, a received signal such as a text messageor web page download will be processed by the communication subsystem1011 and input to the processor 1038, which may further process thereceived signal for output to the display 1022, or alternatively to anauxiliary I/O device 1028.

A user of UE 1000 may also compose data items such as email messages forexample, using the keyboard 1032, which may be a complete alphanumerickeyboard or telephone-type keypad, among others, in conjunction with thedisplay 1022 and possibly an auxiliary I/O device 1028. Such composeditems may then be transmitted over a communication network through thecommunication subsystem 1011.

For voice communications, overall operation of UE 1000 is similar,except that received signals would typically be output to a speaker 1034and signals for transmission would be generated by a microphone 1036.Alternative voice or audio I/O subsystems, such as a voice messagerecording subsystem, may also be implemented on UE 1000. Although voiceor audio signal output is preferably accomplished primarily through thespeaker 1034, display 1022 may also be used to provide an indication ofthe identity of a calling party, the duration of a voice call, or othervoice call related information for example.

Serial port 1030 in FIG. 10 would normally be implemented in a personaldigital assistant (PDA)-type UE for which synchronization with a user'sdesktop computer (not shown) may be desirable, but is an optional devicecomponent. Such a port 1030 would enable a user to set preferencesthrough an external device or software application and would extend thecapabilities of UE 1000 by providing for information or softwaredownloads to UE 1000 other than through a wireless communicationnetwork. The alternate download path may for example be used to load anencryption key onto the device through a direct and thus reliable andtrusted connection to thereby enable secure device communication. Aswill be appreciated by those skilled in the art, serial port 1030 canfurther be used to connect the UE to a computer to act as a modem or forcharging purposes.

Other communications subsystems 1040, such as a short-rangecommunications subsystem, is a further optional component which mayprovide for communication between UE 1000 and different systems ordevices, which need not necessarily be similar devices. For example, thesubsystem 1040 may include an infrared device and associated circuitsand components or a Bluetooth™ communication module to provide forcommunication with similarly enabled systems and devices. Subsystem 1040may further include non-cellular communications such as WiFi or WiMAX,or near field communications (NFC), among others.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis application. This written description may enable those skilled inthe art to make and use embodiments having alternative elements thatlikewise correspond to the elements of the techniques of thisapplication. The intended scope of the techniques of this applicationthus includes other structures, systems or methods that do not differfrom the techniques of this application as described herein, and furtherincludes other structures, systems or methods with insubstantialdifferences from the techniques of this application as described herein.

1. A method at a user equipment comprising: receiving, at the userequipment, a measurement object from a network element for modifying anexisting measurement object at the user equipment; and maintaining atleast one of a measurement reporting entity, associated timers and anyassociated information if the received measurement object is onlymodified to configure cell global identifier reporting.
 2. The method ofclaim 1, further comprising: removing the measurement reporting entity,stopping any associated timers and resetting any associated informationif the received measurement object is modified other than to onlyconfigure cell global identifier reporting.
 3. The method of claim 1,wherein the received measurement object contains and information elementto configure cell global identifier reporting.
 4. The method of claim 1,wherein the received measurement object contains an explicit indicationfor a frequency for reporting the cell global identifier.
 5. The methodof claim 4, wherein the explicit indication is a field within aninformation element for the received measurement object.
 6. The methodof claim 5, wherein the explicit indication is an index value.
 7. Themethod of claim 4, wherein the received measurement object contains animplicit indication for a frequency for reporting the cell globalidentifier.
 8. The method of claim 7, wherein the implicit indicationuses an ordering of frequencies within the measurement object.
 9. Themethod of claim 8, wherein the implicit indication is a frequency at astart of a list of frequencies.
 10. The method of claim 7, wherein theimplicit indication is a starting frequency value.
 11. The method ofclaim 1, further comprising receiving a new measurement identifier andreporting configuration for reporting the cell global identifier fromthe network element.
 12. A user equipment comprising: a processor; and acommunications subsystem, wherein the user equipment is configured to:receive a measurement object from a network element for modifying anexisting measurement object at the user equipment; and maintain at leastone of a measurement reporting entity, associated timers and anyassociated information if the received measurement object is onlymodified to configure cell global identifier reporting.
 13. The methodof claim 12, wherein the user equipment is further configured to: removethe measurement reporting entity, stop any associated timers and resetany associated information if the received measurement object ismodified other than to only configure cell global identifier reporting.14. The user equipment of claim 12, wherein the received measurementobject contains and information element to configure cell globalidentifier reporting.
 15. The user equipment of claim 12, wherein thereceived measurement object contains an explicit indication for afrequency for reporting the cell global identifier.
 16. The userequipment of claim 15, wherein the explicit indication is a field withinan information element for the received measurement object.
 17. The userequipment of claim 16, wherein the explicit indication is an indexvalue.
 18. The user equipment of claim 13, wherein the receivedmeasurement object contains an implicit indication for a frequency forreporting the cell global identifier.
 19. The user equipment of claim18, wherein the implicit indication uses an ordering of frequencieswithin the measurement object.
 20. The user equipment of claim 19,wherein the implicit indication is a frequency at a start of a list offrequencies.
 21. The user equipment of claim 18, wherein the implicitindication is a starting frequency value.
 22. The user equipment ofclaim 12, further comprising receiving a new measurement identifier andreporting configuration for reporting the cell global identifier fromthe network element. 23.-62. (canceled)